docs: steer large/long documents to streaming#10
Merged
Conversation
…be dropped by an intermediary ~340s; the SSE path is kept alive server-side)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to #9 (900s timeout, already merged). This README note was pushed to the #9 branch after it merged, so it never reached main. For large/long documents, streaming is the actual remedy: the server keep-alives SSE connections (ping every 15s), whereas a long buffered request is dropped by an intermediary at ~340s (verified: a 45-page doc dies buffered at ~340s, completes streamed in ~273s).